Monitoring system configuration technology

ABSTRACT

An electronic system is described that receives data identifying a component of a monitoring system from a wearable electronic device that is associated with the monitoring system. The monitoring system is associated with a property and includes components that are fixed within the property and that are configured to sense attributes of the property. The wearable electronic device includes a heads-up display and communicates with the monitoring system over a wireless network. Based on the data identifying the component of the monitoring system, monitoring system data collected by the component of the monitoring system is accessed. At least a portion of the monitoring system data collected by the component of the monitoring system is provided to the wearable electronic device for display at the heads-up display of the wearable electronic device.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from U.S. Provisional Application No.61/974,232, filed Apr. 2, 2014, and titled “MONITORING SYSTEMCONFIGURATION TECHNOLOGY,” which is hereby incorporated by reference inits entirety.

TECHNICAL FIELD

This application relates to data communication between devices.

BACKGROUND

A monitoring system for a property can include various componentsincluding sensors, cameras, and other devices that enable monitoring ofthe property. A user can modify the monitoring system by adding,removing, or reconfiguring components of the monitoring system.

SUMMARY

Techniques are described for assisting a user who is modifying amonitoring system to add or configure a component of the monitoringsystem.

Implementations of the described techniques may include hardware, amethod or process implemented at least partially in hardware, or acomputer-readable storage medium encoded with executable instructionsthat, when executed by a processor, perform operations.

The details of one or more implementations are set forth in theaccompanying description below. Other features will be apparent from thedescription of the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system that assists with configuringa component of a monitoring system.

FIG. 2 depicts an example system that is capable of assisting with theconfiguring of a component of a monitoring system.

FIG. 3 depicts a flow chart of an example process.

FIG. 4 illustrates an example of a system that assists with theconfiguring of a monitoring system using data from two or morecomponents of a monitoring system.

FIGS. 5A and 5B illustrate examples of a system that assists withmonitoring system configuration by enabling remote testing of acomponent of the monitoring system.

DETAILED DESCRIPTION

Techniques are described for performing monitoring system configurationusing a wearable electronic device, such as a device that includes aheads-up display (HUD). In some implementations, a HUD device is able totransmit and receive data from a monitoring system that is associatedwith a home, business, vacation, or other property. In someimplementations, the monitoring system can be associated with one ormore cameras, sensors, or other components, such as locks, appliances,heating, ventilation, and air conditioning (HVAC) systems, or otherdevices associated with the property. A wearable electronic deviceequipped with a HUD includes a software application that enables thedevice to communicate with the monitoring system. The device cantransmit data to, and receive data from, components of the monitoringsystem, such as video footage obtained by one or more video camerasassociated with the monitoring system or sensor data obtained by one ormore sensors associated with the monitoring system. Communicationbetween the device and the components of the monitoring system can aidprocesses associated with configuring the monitoring system. Inaddition, a user of a wearable electronic device equipped with a HUD cancontrol the monitoring system or components of the monitoring systemusing the device.

In some implementations, an installer or other user can use a wearableelectronic device that features a HUD when configuring or installingcomponents of a monitoring system to ensure that the monitoring systemcomponents are properly installed and functional to perform theirdesignated tasks. For example, while installing a monitoring systemcamera, an installer can associate a wearable electronic devicefeaturing a HUD with the monitoring system, and can configure the deviceto display the camera's field of view in the device's HUD. Since theinstaller is able to view the camera's field of view while activelyinstalling the camera, the installer can configure the camera to havethe desired field of view with limited additional effort. For example,if the camera to be installed is located in a hard-to-reach area of aproperty, such as a roof of the property, the installer may be able toadjust the camera's field of view from the location of the camera whileinstalling the camera. That is, the installer may be able to activelyadjust the positioning of the camera and view changes to the camera'sfield of view in near real time, without having to iteratively check thecamera's field of view at another location and return to the camera toadjust its view.

In other examples, an installer of a monitoring system can install asensor associated with the monitoring system, and can utilize a wearabledevice featuring a HUD to test the functionality of the sensor duringthe installation process and without the inefficiency of testing thesensor's functionality from, for example, a control panel of themonitoring system. The installer can receive data at the HUD thatindicates whether the test was successful, or may be presented withinformation that enables the installer to perfect the installation ofthe sensor.

FIG. 1 illustrates an example of a system 100 that assists with theinstallation and configuration of a component of a monitoring system.For example, a monitoring system that is associated with a property mayinclude a monitoring system control unit 110 that is in communicationwith one or more sensors, cameras, or other components of the monitoringsystem. The monitoring system control unit 110 can include one or morecontrol panels, servers, or other computer systems that are configuredto receive, process, and/or transmit data related to the operation ofthe monitoring system.

In FIG. 1, an installer 102 equipped with a wearable electronic device150 that includes a HUD 152 is adding a camera 130 to the monitoringsystem associated with the property. The installer 102 may, for example,be installing the camera 130 at a location of the property, where thecamera 130 is to be configured to monitor a certain area of theproperty, such as a picnic area of the property. In some instances, theinstaller 102 may be required to install the camera 130 at location thatis difficult to access, or a location that is distant from any controlpanel or other control device associated with the monitoring system. Forexample, in order for the camera 130 to monitor the picnic area of theproperty, the installer 102 may need to attach the camera 130 to a roofof the property being monitored by the monitoring system.

After the installer 102 has physically mounted the camera 130 and hasactivated the camera 130 such that the monitoring system can communicatewith the camera 130, the installer 102 must test the camera 130 toensure that the camera 130 is functioning, that the field of view 135 ofthe camera 130 is directed in the proper direction so as to include thepicnic area of the property, and/or that images or video captured by thecamera 130 are of the necessary clarity to enable effective monitoringof the picnic area of the property. While the installer 102 may be ableto perform such a function by testing the camera 130 or viewing theimages or video obtained by the camera 130 at a control panel or othercomputing device associated with the monitoring system control unit 110,it is advantageous for the installer 102 to test the camera 130 from thelocation at location of the camera 130. By doing so, the installer 102may be able to directly adjust the field of view 135 of the camera 130,may be able to troubleshoot the camera's 130 wiring or configuration ifthe camera 130 is not functioning properly, or may be able to adjust theimage or video capture parameters used by the camera 130 if the imagesor video obtained by the camera are not sufficiently clear.

To test the camera 130 from the location of the camera 130, theinstaller 102 interacts with their wearable electronic device 150 tocause images, video, or other information obtained by or relevant to thecamera 130 to be displayed at the HUD 152 of the wearable electronicdevice 150. Once the installer 102 has installed the camera 130, theinstaller 102 can activate the camera 130, for example, by powering onthe camera 130 and activating the camera 130 to enable the camera 130 tocommunicate with the monitoring system control unit 110. The installer102 can also activate their wearable electronic device 150 to be incommunication with the monitoring system control unit 110, for example,by turning on the wearable electronic device 150, activating anapplication on the wearable electronic device 150 that is associatedwith interacting with the monitoring system, connecting the wearableelectronic device 150 to the monitoring system control unit 110 over oneor more networks, or otherwise configuring the wearable electronicdevice 150 to communicate with the monitoring system control unit 110.

Based on both the wearable electronic device 150 and the camera 130being in communication with the monitoring system control unit 110, theinstaller 102 provides input at the wearable electronic device 150 thatidentifies the camera 130 and requests information related to the camera130 (Step A). For example, the installer 102 can provide input to thewearable electronic device 150 that identifies the camera 130 from amongone or more other components of the monitoring system, such as one ormore other cameras, sensors, controllers, or other monitoring systemcomponents. The installer 102 may also request specific data from orrelating to the camera 130. For instance, in FIG. 1 the installer 102requests video data obtained by the camera 130, so that the installer102 may adjust the field of view 135 of the camera 130 to focus on thepicnic area of the property that the monitoring system is configured tomonitor. Additionally or alternatively, the installer 102 may requestother data from or relating to the camera 130, for example, dataindicating the strength of a network connection used by the camera 130to communicate with the monitoring system control unit 110, dataindicating a rate of data communication between the camera 130 and themonitoring system control unit 110, data indicating a state of thecamera 130, data indicating the battery state of the camera 130, orother data relevant to the camera 130.

The monitoring system control unit 110 receives the information from thewearable electronic device 150 that identifies the camera 130. Based onthis received information, the monitoring system control unit 110transmits a request for video data to the camera 130 (Step B). Themonitoring system control unit 110 can receive the request, and inresponse can transmit video data obtained by the camera 130 to themonitoring system control unit 110 (Step C).

In some implementations, the information requested by the installer 102may be information that does not require the monitoring system controlunit 110 to transmit a request to the camera 130, or that may notrequire the monitoring system control unit 110 to receive informationfrom the camera 130. For example, in some implementations the camera 130may transmit video data to the monitoring system control unit 110without the monitoring system control unit 110 requesting the videodata, such that the monitoring system control unit 110 is not requiredto transmit a request to the camera 130 to obtain the video data. Inanother example, the monitoring system control unit 110 may be capableof determining the information requested by the installer 102 withouthaving to request information from the camera 130. For instance, themonitoring system control unit 110 may be capable of testing thestrength of a wireless network connection between the camera 130 and themonitoring system control unit 110 without a need to request and/orreceive information from the camera 130. Similarly, the monitoringsystem control unit 110 may be capable of determining whether the camera130 has power without communicating with the camera 130 directly.

In some implementations, the monitoring system control unit 110 mayrequest and/or receive information from the camera 130 that is differentfrom the information requested by the installer 102. The monitoringsystem control unit 110 may then perform an analysis of the informationreceived from the camera 130, to determine a response to the requestprovided by the installer 102. For instance, if the installer 102requests information indicating the strength of a network connectionbetween the monitoring system control unit 110 and the camera 130, themonitoring system control unit 110 may communicate test data with thecamera 130, for example, by transmitting a small packet of data to thecamera 130 and receiving a response to the transmission that is anotherpacket of data. The monitoring system control unit 110 may then performan analysis, for instance, to determine how much time was required tosend and receive the data packets, thereby determining the strength ofthe network.

The monitoring system control unit 110 provides a reply to the wearableelectronic device 150 that includes a response to the request of theinstaller 102 (Step D). For example, as shown in FIG. 1, in response tothe installer 102 requesting the video data obtained by the camera 130,the monitoring system control unit 110 transmits the video data obtainedfrom the camera 130 to the wearable electronic device 150. The wearableelectronic device 150 then provides the received video data for displayat the HUD 152 of the wearable electronic device 150. By receiving thevideo of the camera 130 in the HUD 152 of the wearable electronic device150 that the installer 102 is wearing, the installer 102 is providedwith a hands-free solution in which they are able to adjust the field ofview 135 of the camera 130 while being able to view the effects of thoseadjustments in near real-time.

In other examples, the information provided by the monitoring systemcontrol unit 110 to the wearable electronic device 150 can be otherinformation configured for display at the HUD 152 of the wearableelectronic device 150. For example, if the installer 102 requests to doa test of the camera 130, the monitoring system control unit 110 cantransmit information to the wearable electronic device 150 thatindicates whether the camera 130 successfully completed the test. Thewearable electronic device 150 can provide information for display atthe HUD 152 that indicates whether the test was successful, and mayadditionally provide other information relating to the request of theinstaller 102. For example, the monitoring system control unit 110 mayprovide information for display at the HUD 152 of the wearableelectronic device 150 that indicates that a test of the camera 130 wasunsuccessful, and additionally providing possible reasons why the camera130 failed the test or steps to troubleshoot the camera 130.

FIG. 2 illustrates an example of a monitoring system 200 configured tocommunicate with a wearable device that features a heads-up display. Themonitoring system 200 includes a network 205, a monitoring control unit210, one or devices 240, 250 including the HUD device 250, a monitoringapplication server 260, and one or more components that are interfacedwith the monitoring control unit 210 via the module 230.

The network 205 is configured to enable electronic communicationsbetween devices connected to the network 205. For example, the network205 can be configured to enable the exchange of electroniccommunications between the monitoring control unit 210, the one or moredevices 240, 250, and the monitoring application server 260.

The network 205 can include, for example, one or more of the Internet,Wide Area Networks (WANs), Local Area Networks (LANs), e.g., Wi-Fi,ZigBee, or Z-Wave networks, analog or digital wired and wirelesstelephone networks, e.g., a public switched telephone network (PSTN),Integrated Services Digital Network (ISDN), a cellular network, andDigital Subscriber Line (DSL), Ethernet, Internet Protocol (IP) overbroadband, radio, television, cable, satellite, or any other delivery ortunneling mechanism for carrying data. Network 205 can include multiplenetworks or subnetworks, each of which can include, for example, a wiredor wireless data pathway. The network 205 can include a circuit-switchednetwork, a packet-switched data network, or any other network able tocarry electronic communications (e.g., data or voice communications).For example, the network 205 can include networks based on the Internetprotocol (IP), asynchronous transfer mode (ATM), the PSTN,packet-switched networks based on IP, X.25, or Frame Relay, or othercomparable technologies and can support voice using, for example, VoIP,or other comparable protocols used for voice communications. The network205 can include one or more networks that include wireless data channelsand wireless voice channels. The network 205 can be a wireless network,a broadband network, or a combination of networks including a wirelessnetwork and a broadband network.

The monitoring control unit 210 includes a controller 212 and a networkmodule 214. The controller 212 is configured to control a device systemthat includes the control unit 210, e.g., one or more cameras, sensors,or other components associated with a property's monitoring system. Insome examples, the controller 212 can include a processor or othercontrol circuitry configured to execute instructions of a program thatcontrols operations of one or more cameras, sensors, or other componentsof the monitoring system. In these examples, the controller 212 can beconfigured to receive input from one or more devices 240, 250 associatedwith the property, and can control the configuration or operation of oneor more components associated with the monitoring system based on theinput received from the devices 240, 250. For example, the controller212 may receive input configuring a particular camera associated withthe monitoring system 200 from a HUD device 250, and can configure thefield of view of the particular camera based on the input received fromthe HUD device 250.

The network module 214 is a communication device configured to exchangecommunications over the network 205. The network module 214 can be awireless communication module configured to exchange wirelesscommunications over the network 205. For example, the network module 214can be a wireless communication device configured to exchangecommunications over a wireless data channel. In this example, thenetwork module 214 can transmit sensor data captured by one or morecameras or sensors of the monitoring system 200, data associated withcontrolling one or more other components of the monitoring system 200,data associated with configuring one or more cameras, sensors, or othercomponents associated with the monitoring system 200, data associatedwith users of the property, or other information over a wireless datachannel. The wireless communication device can include one or more GSMmodules, a radio modem, a cellular transmission module, or any type ofmodule configured to exchange communications in one of the followingformats: GSM or GPRS, CDMA, EDGE or EGPRS, EV-DO or EVDO, UMTS, or IP.

The network module 214 can also be a wired communication moduleconfigured to exchange communications over the network 205 using a wiredconnection. For instance, the network module 214 can be a modem, anetwork interface card, or another type of network interface device. Thenetwork module 214 can be an Ethernet network card configured to enablethe monitoring control unit 210 to communicate over a local area networkand/or the Internet. The network module 214 can also be a voicebandmodem configured to enable the monitoring control unit 210 tocommunicate over the telephone lines of Plain Old Telephone Systems(POTS). In some implementations, the monitoring control unit 210 can bea broadband or cellular gateway where the network module 214 can enablethe monitoring control unit 210 to communicate over the network 205.

The module 230 is connected to one or more cameras, sensors, or othercomponents of the monitoring system 200 that are configured to monitorand/or control various aspects of a property. For example, camerasand/or sensors associated with the monitoring system 200 may beconfigured to monitor activity and/or conditions in various zones of aproperty (e.g., at various indoor or outdoor locations of the property).For example, cameras connected to the module 230 can include variousvideo, still-image, infrared, night-vision, or other cameras that areconfigured to monitor activity at a property. Sensors connected to themodule 230 may include various activity sensors, such as motion sensors,contact sensors, etc., or may additionally or alternatively includevarious environmental sensors, such as temperature sensors, humiditysensors, noise sensors, light sensors, air quality sensors, smokedetectors, carbon monoxide detectors, water sensors, rain sensors, windsensors, etc. Other components associated with the monitoring system 200can include door and window locks, furnaces, air conditioners, ovens andstovetops, fans, garage doors, etc. The module 230 connected to the oneor more cameras, sensors, or other components can exchange electroniccommunications with the monitoring control unit 210. For example, avideo camera can communicate video data to the monitoring control unit210 via the module 230 and/or can receive data directed to configuringor controlling the video camera from the monitoring control unit 210 viathe module 230.

The module 230 can communicate with the controller 212 over thecommunications link 222. The communication link 222 can be a wired orwireless data pathway configured to transmit signals from the module 230to the monitoring control unit 210. The module 230 can continuouslytransmit and receive data from the controller 212, can periodicallytransmit and receive data from the controller 212, or can transmit andreceive data from the controller 212 in response to detecting events,e.g., in response to detecting a change in a sensed value by a sensor ofthe monitoring system. The cameras, sensors, and other components of themonitoring system that are in communication with the monitoring controlunit 210 via the module 230 can continuously or periodically transmitand receive information from the module 230, or can transmit and receiveinformation from the module 230 in response to detecting a specificevent (e.g., an event at the property or an error relating to one ormore of the cameras, sensors, or other components).

In some implementations, cameras, sensors, or other components cancommunicate directly with the monitoring control unit 210. For example,the monitoring control unit 210 can communicate with a camera, sensor,or other component of a monitoring system to send and/or receiveinformation related to controlling the camera, sensor, or component,information identifying the status of the camera, sensor, or component,or other information. In some instances, the monitoring control unit 210can communicate information directly to both the module 230 and one ormore cameras, sensors, and/or other components.

The monitoring application server 260 is an electronic device configuredto provide monitoring services and enable monitoring systemconfiguration by exchanging electronic communications with themonitoring control unit 210 and the one or more devices 240, 250 overthe network 205. For example, the monitoring application server 260 canbe configured to receive video data obtained by the monitoring controlunit 210. In this example, the monitoring application server 260 canexchange electronic communications with the network module 214 includedin the monitoring control unit 210 to receive video data obtained by oneor more cameras of the monitoring system 200 that are in communicationwith the monitoring control unit 210. The monitoring application server260 can transmit the obtained video data to one or more of the devices240, 250, such as by transmitting the video data obtained by the one ormore cameras to the HUD device 250. Additionally, the monitoringapplication server 260 can receive information from the one or moredevices 240, 250. For example, the monitoring application server 260 canreceive information from the one or more mobile devices 240, 250 thatindicates the locations of the one or more devices 240, 250 or thatincludes commands requested by users of the one or more devices 240,250. In some implementations, the monitoring application server 260 canreceive information from one or more other sources. For example, themonitoring application server 260 can receive information over thenetwork 205 relating to events that are potentially relevant to theproperty (e.g., weather data, crime data, etc.).

In some implementations, the monitoring application server 260 can beconnected to the Internet over the network 205 and can accessinformation at a website or database that is accessible on the Internet.Additionally or alternatively, the monitoring application server 260 canstore information at a local database or other data storage componentand can access the stored information. For example, the monitoringapplication server 260 can access installation instructions ortroubleshooting instructions relating to cameras, sensors, or othercomponents of the monitoring system 200 at a website or database that isaccessible via the Internet. The monitoring application server 260 canaccess the installation or troubleshooting instructions and can transmitinformation associated with the instructions to one or more devices 240,250, for example, by causing the installation or troubleshootinginstructions to be presented in the HUD of the HUD device 250.

The monitoring application server 260 can store data (e.g., video orimage data obtained by cameras of the monitoring system 200, sensor datafrom sensors of the monitoring system 200, or performance data fromappliances or HVAC system components associated with the monitoringsystem 200) and can perform analysis of the stored data. Based on theanalysis, the monitoring application server 260 can communicate with andcontrol components of the monitoring system 200, such as one or morecameras, sensors, or other components that are connected to themonitoring control unit 210 via the module 230.

The one or more devices 240, 250 are devices that host one or morenative applications (e.g., the native control applications 242, 252).The one or more devices 240, 250 can be cellular phones or non-cellularlocally networked devices. The one or more devices 240, 250 can includea cell phone, a smart phone, a tablet PC, a personal digital assistant(“PDA”), a wearable computing device, or any other stationary orportable device configured to communicate over a network. For example,implementations can also include Blackberry-type devices (e.g., asprovided by Research in Motion), electronic organizers, iPhone-typedevices (e.g., as provided by Apple), iPod devices (e.g., as provided byApple), or other portable music players, other communication devices,and handheld, wearable, or portable electronic devices for gaming,communications, and/or data organization. The one or more devices 240,250 can be the same or can include mobile devices of different types.The one or more devices 240, 250 can perform functions unrelated to themonitoring system, such as placing personal telephone calls, playingmusic, playing video, displaying pictures, browsing the Internet,maintaining an electronic calendar, etc. The devices 240, 250 include atleast one HUD device 250, where the HUD device is a wearable electronicdevice that is capable of displaying information in a HUD, of hostingthe native control application 252, and of communicating with one ormore components of the monitoring system 200. In some implementations,the HUD device 250 can feature one or more cameras, and/or one or moremeans of providing user input, e.g., via a touch screen, by usinggestures, or using other inputs. For example, the HUD device 250 can bean optical head-mounted display (OMHD) device that displays informationand enables user interaction in a hands-free format by using naturallanguage voice commands, gestures, or other actions, and that cancommunicate with one or more components of the monitoring system 200using wireless connections. In some examples, the HUD device 250 may bea device similar to Google Glass, or another OMHD device.

In some implementations, the HUD device 250 that features the nativecontrol application 252 may enable users to interact with the device inspecific ways to control the monitoring system or to navigate within thenative control application 252. For example, the native controlapplication 252 may enable users to provide inputs by using head nodgestures. As an example, a head nod in a particular direction may causethe native control application 252 to navigate through menus, to zoom inor out on particular information in the HUD, to toggle the display ofinformation relating to various components of the monitoring system, toactivate or deactivate the monitoring system 200, etc.

In some implementations, the one or more devices 240, 250 cancommunicate with the monitoring control unit 210 via the communicationlink 224. For instance, the one or more devices 240, 250 can communicatewith the monitoring control unit 210 using various local wirelessprotocols, such as Wi-Fi, Bluetooth, Z-Wave, ZigBee, HomePlug (Ethernetover powerline), or wired protocols such as Ethernet, USB, and otherwired protocols based on the RS232, RS485, and/or RS422 standards. Theone or more devices 240, 250 can connect locally to the monitoringcontrol unit 210 and/or other components of the monitoring system 200(e.g., one or more cameras, sensors, or other components). The localconnection can improve the speed of communications because communicatingthrough the network 205 with a remote server (e.g., the monitoringapplication server 260), can be slower.

Although the one or more devices 240, 250 are shown communicating withthe monitoring control unit 210, in some implementations, the one ormore devices 240, 250 can communicate directly with the cameras,sensors, and other components that are in communication with themonitoring control unit 210. In some implementations, the one or moredevices 240, 250 replace the monitoring control unit 210 and perform thefunctions of the monitoring control unit 210 for local control and longrange or offsite communication and/or control.

In other implementations, the one or more devices 240, 250 receive datafrom the monitoring control unit 210 through the network 205. The one ormore devices 240, 250 can receive the data from the monitoring controlunit 210 through the network 205 or from the monitoring applicationserver 260 and can transmit or relay data to the monitoring control unit210 or the monitoring application server 260 through the network 205. Inthis regard, the monitoring application server 260 can facilitatecommunications between the one or more devices 240, 250 and themonitoring control unit 210.

Although the one or more devices 240, 250 are shown in FIG. 2 as beingconnected to the network 205, in some implementations, the one or moredevices 240, 250 are not connected to the network 205. In theseimplementations, the one or more devices 240, 250 may communicatedirectly with one or more of the monitoring system components withoutrequiring a network connection.

In some implementations, the one or more devices 240, 250 are used inconjunction with only local cameras, sensors, and other components of aproperty's monitoring system. In these implementations, the monitoringsystem 200 only includes the one or more devices 240, 250 and the module230. The one or more devices 240, 250 can receive data directly from themodules 230 and/or the components connected to the module 230, and cansend data directly to the module 230 and/or the components connected tothe module 230. The one or more mobile devices 240, 250 provide theappropriate interfaces and/or processing to provide for control of themonitoring system, including capabilities to modify monitoring systempreferences, control monitoring system components, respond to eventsdetected by the monitoring system, etc.

The one or more devices 240, 250 each include a native controlapplication 242, 252, respectively. The native control application 242,252 refers to a software/firmware program running on the correspondingdevice that enables the described features. The one or more devices 240,250, including the HUD device 250, can load or install the nativecontrol application 242, 252 based on data received over a network ordata received from local media. The native monitoring application 242,252 can run on mobile devices' platforms, such as Apple iOS, iPhone,iPod touch, Blackberry, Google Android, Windows Mobile, Mobile Linux,Firefox OS, etc.

The described technology for configuring a monitoring system enables auser having a device with a heads-up display to view informationassociated with the monitoring system directly in the heads-up display,and to control or otherwise interact with the monitoring system usingthe device. By enabling the user to view information associated with themonitoring system and to interact with the monitoring system via the HUDdevice, a user can install monitoring system cameras, sensors, and othercomponents with greater efficiency than in scenarios when the user mustphysically install the cameras, sensors, or components in one location,and must test and configure the cameras, sensors, and other componentsat a different location.

In some implementations, as described, an electronic device featuring aHUD is capable of running an application that enables users to interactwith a property's monitoring system via the HUD device. For example, theHUD device 250 may feature a heads-up display and one or more methods ofinteracting with the HUD device 250, such as a touchscreen, buttons,joystick, voice interface, capabilities to detect a user's movements orgestures, capabilities to track a user's eye movements, or otherinteraction mechanism. The HUD device 250 can run a native controlapplication 252 that enables the HUD device 250 to communicate with themonitoring application server 260, monitoring control unit 210, and/orother components of the monitoring system 200. In some applications, auser associated with the HUD device 250 can launch the native controlapplication 252 while using the HUD device 250, for example, byproviding an input at a touchscreen of the HUD device 250 or byproviding a voice command that causes the native control application 252to launch.

When the HUD device 250 is running the native control application 252,the HUD device 250 can receive information relating to the monitoringsystem 200 and can display the received information in the device's HUD.For instance, the HUD device 250 can receive images or video obtained byone or more cameras associated with the monitoring system 200, dataobtained by one or more sensors of the monitoring system 200, activitylogs of one or more other components of the monitoring system 200,testing results relating to one or more particular cameras, sensors, orother components of the monitoring system 200, installation ortroubleshooting instructions relating to one or more particular cameras,sensors, or other components of the monitoring system 200, or otherinformation relating to the monitoring system 200. The receivedinformation can be presented in the HUD of the HUD device 250.

Additionally, a user associated with the HUD device 250 can provideinputs at the HUD device 250 to perform actions relating to themonitoring system 200. For example, the user may provide input at theHUD device 250 by swiping a touchscreen of the HUD device 250,performing a certain gesture or head movement that is detectable by theHUD device 250, by speaking voice commands that are discernible by theHUD device 250, or by otherwise providing input at the HUD device 250.Based on receiving the user input, the HUD device 250 can transmitinformation related to the user inputs to the monitoring applicationserver 260, monitoring control unit 210, or other components of themonitoring system 200 to perform the requested actions.

A HUD device that is in communication with a monitoring system candisplay images or video captured by a particular camera or video cameraassociated with the monitoring system in the device's HUD. For example,an installer of the monitoring system 200 can be equipped with HUDdevice 250, and can be in the process of installing a video camera inthe monitoring system 200. The video camera can communicate with themonitoring system 200 via the module 230. After connecting the videocamera to the monitoring system 200, the installer may configure thevideo camera, for example, by adjusting the video camera's field ofview, color balance, contrast, brightness, or other image propertiesassociated with the video camera, or the installer may otherwise testwhether the video camera is functioning properly in the monitoringsystem 200. In some implementations, after the installer has connectedthe video camera to the monitoring system 200, the installer can provideinput that causes a video feed from the installed camera to be projectedat the HUD of the HUD device 250. Since the HUD device 250 can receiveand display the video camera's field of view to the installer while theinstaller is at the site of the video camera, the installer may be ableto configure the video camera from the location of the video camerawhile being able to view the results of configuring the camera in nearreal time. For example, as the user adjusts the video camera's field ofview by tilting or mounting the video camera in a new location, theinstaller may be able to view the video camera's new field of view todecide if the new tilt or positioning of the video camera provides anacceptable field of view for the monitoring system 200 to functionproperly. Similarly, an installer may be able to adjust the colorsettings of a particular video camera by displaying a color chart to thevideo camera, and performing processing on the colors detected by thevideo camera to tune the video camera's color settings.

Additionally, in some implementations an installer of the monitoringsystem 200 may request and view information associated installing orconfiguring a component of the monitoring system. For example, aninstaller that is installing a camera in the monitoring system 200 mayprovide input to the HUD device 250 that identifies the particularcamera, a model of the particular camera, or other information thatidentifies the camera that the installer is installing. In response,installation or configuration instructions for the camera, instructionalvideos or images related to the installation or configuration of thecamera, or other installation information can be accessed. For instance,the monitoring application server 260 may receive informationidentifying the model of the camera, and may access installationinstructions or an instructional video related to installing theparticular model of camera. At least a portion of the accessedinstallation information can be provided for output at the HUD device250 to provide the installer with information on how to install thecamera while they are actively doing so. In another example, theinstaller may request information related to configuring the camera,such as configuring the camera's contrast, white balance, or other imageor video capture parameters. The monitoring application server 260 oranother element of the monitoring system 200 may identify informationthat indicates how to configure the camera, information indicating howchanges to certain parameters affect the operation or images captured bythe camera, or other information related to configuring the camera. Theaccessed information can be presented to the installer at the HUD device250 to allow the installer to view this information while they areconfiguring the camera.

In some implementations, a user or installer may be able to control thepan and tilt of a video camera from the HUD device 250, such that thevideo camera's field of view can be adjusted to coincide or nearlycoincide with the user's field of view from the HUD device 250. In suchan implementation, a camera of the HUD device 250 can capture imagedata, and the pan and tilt of the video camera can be adjusted to matchthe field of view of the camera of the HUD device 250. In otherimplementations, a user or installer may provide input at the HUD device250 to control the pan and tilt of the video camera. For instance, auser may perform a particular gesture, such as by nodding their head ina particular direction, to adjust the pan and tilt of the HUD device 250based on the input (e.g., such that a user nodding their head to theleft causes the video camera to pan to the left).

Furthermore, in some implementations, a user equipped with a HUD devicemay be able to provide commands at the HUD device that control thedisplay of data at the HUD device. For example, an installer having theHUD device 250 and who is installing a video camera in the monitoringsystem 200 may be able to provide input at the HUD device 250 toalternate between viewing various types of data for the video camerathat is being installed. For instance, the installer may first requestto view the video feed obtained by the video camera that they areinstalling, and may subsequently request to view the battery life of thevideo camera they are installing. The installer may provide input at theHUD device 250 that causes the information presented to the installer tochange from the video feed of the video camera to data indicating theremaining battery life of the video camera.

Additionally, the installer may be able to provide input at the HUDdevice 250 to alternate between viewing data associated with the videocamera being installed and data associated with other components of themonitoring system 200. For example, the installer equipped with the HUDdevice 250 may desire to optimize the fields of view of two or morevideo cameras to provide an optimal view of a particular zone of theproperty associated with the monitoring system 200. To aid in optimizingthe collective field of view of the video cameras, the installer mayprovide input at the HUD device 250 that causes the HUD device 250 todisplay the video feeds of one or more of the video cameras that aremonitoring the particular zone of the property. In some instances, theuser may provide input at the HUD device 250 that causes the video feedsof two or more cameras to be displayed simultaneously in the HUD of theHUD device 250, may provide input to cycle through the video feeds oftwo or more of the video cameras, may provide input that selects aparticular camera's field of view for display in the HUD, or mayconfigure the video feeds of the cameras to be presented in the HUD inother ways.

The video data displayed to an installer or user can be configured tostream continuously to the HUD device, or can be presented to the useror installer as a sequence of frames that are updated periodically. Forexample, the HUD device 250 associated with the installer may receiveone image every second from the video feed of a video camera of themonitoring system 200, and may present the stream of images to the userin the HUD of the HUD device 250. In some instances, the frequency thatimages are obtained from the video feed and transmitted to the HUDdevice 250, or the quality of the images that are obtained from thevideo feed and transmitted to the HUD device 250, can be dependent uponuser preferences, network connectivity of the HUD device 250, upon theremaining battery life of the HUD device 250 and/or the video cameraproviding the video feed, or based upon other factors. For example, auser may set a preference (e.g., at the native control application 252)that dictates how frequently images from the video feed of the videocamera are transmitted to the HUD device 250 (e.g., ranging from acontinuous stream at 30 frames per second to intermittent images thatare updated once every 5 seconds). Similarly, the user may set apreference related to the image quality of the images displayed at theHUD device 250 (e.g., ranging from high-resolution at 1920×1080 pixelsto low resolution at 848×480 pixels). In other implementations, userpreferences may be combined with or superseded by frame rate and imagequality settings that are dependent upon network connectivity and/orvideo camera or HUD device battery life. For example, the HUD device 250may display lower resolution images less frequently while a networkconnection of the HUD device 250 to the network 205 is weak and/orbattery life of the HUD device 250 is low, and will display higherresolution images at a greater frame rate when the network connection isstrong and/or battery life is adequate. In some instances, the imagespresented at the HUD of the HUD device 250 may be all of the imagesobtained by a particular camera or may be a subset of the imagesobtained by the camera. For example, if the camera is obtaining video,all of the frames of video may transmitted to the HUD device 250, theHUD device may present frames periodically obtained from the video,e.g., every fiftieth frame of the video. In other examples, a camerathat obtains images once every second may have all of these imagespresented at the HUD device 250, or may have a subset of these imagespresented at the HUD device 250.

In some implementations of the described subject matter, a user equippedwith a HUD device that is in communication with a monitoring system canconfigure the HUD device to display data relating to tests performed oncomponents of the monitoring system. For instance, an installer who isinstalling a sensor in the monitoring system 200 may be equipped with aHUD device 250, and after installing the sensor the installer mayperform a test to confirm that the sensor is functioning properly in themonitoring system 200. The installer can connect the sensor to themonitoring system 200 as a part of the installation process and canprovide input at the HUD device 250 to initialize testing of the sensor.Results of the test can be returned to the HUD device 250 and presentedto the installer within the HUD. By presenting test results to theinstaller within the HUD, the installer may be able to view the resultsof the test while maintaining the ability to use their hands; animportant feature when the installer is in a precarious position such asstanding on a ladder, or when the information presented to the installermay enable the installer to reconfigure or otherwise adjust the sensorwhile viewing the information.

In some instances, information presented to an installer as a part oftesting a camera, sensor or other component of the monitoring system 200can include messages indicating whether testing of the camera, sensor,or component was successful. For example, after installing and testing amotion sensor at a property, the installer test the motion sensor todetermine whether the sensor is connected to the monitoring system 200and whether the motion sensor is functioning properly within themonitoring system 200. A message may be displayed to the installer inthe HUD of the HUD device 250 that indicates if the motion sensorsuccessfully passed the test (e.g., by displaying a green check mark andthe message “Successful”) or failed the test (e.g., by displaying a redcross and the message “Failed”).

In some instances, test results presented to the installer within theHUD can include additional details, for example, information indicatingwhether data communications with the sensor were successful, whether thetype of notification provided by a sensor was accurate (e.g., if amotion sensor properly reported motion detection), whether the sensor isrecognized as being associated with a proper sensor group or zone of theproperty (e.g., if a sensor in a kitchen of the property is properlyregistered as being located in the kitchen and not in the garage of theproperty), whether alarms triggered by the sensor are appropriate (e.g.,if triggering of a door sensor causes an intruder alarm to be triggered,and not another alarm type), etc. In some implementations, indicationscan be presented for one or more criteria analyzed in the testingprocess to convey whether the component of the monitoring system 200being tested passed or failed the test with respect to each of thecriteria. For example, a sensor that is identified as passing a test(e.g., a motion sensor properly reporting detected motion) may display agreen check mark and the message “Successful” in associated with certaincriteria, but may present a red cross and the message “Failed” inassociation with other criteria. For example, a motion sensor mayproperly detect motion near the sensor, but may trigger an improperalarm based on detecting the motion. Therefore, criteria associated withmotion detection may be identified as “Successful” tests, while criteriaassociated with providing alarms may be identified as “Failed” tests.

Based on determining that a particular camera, sensor, or component of amonitoring system has failed a test, information can be presented to aninstaller via a HUD device that identifies potential reasons for theerrors and/or instructions for troubleshooting the errors. For example,based on a sensor failing a test after being installed in the monitoringsystem 200, information may be presented to the installer of the sensorvia the HUD device 250 that informs the installer of reasons why thesensor may have failed the test, a message indicating that reconfiguringthe sensor may likely correct the sensor error, and instructions thatteach the installer to reconfigure the sensor. In some implementations,instructions provided to the installer may be presented sequentially(e.g., one step at a time), such that the installer may interact withthe HUD device 250 through voice, gestures, or other inputs to navigatethrough the necessary steps. In some instances, the instructions may bepresented to the user as a combination of visual information presentedin the HUD of the HUD device 250 and audible or other data presented tothe user via a speaker or other component of the HUD device 250.

In some examples, a monitoring system associated with a propertyfeatures one or more devices that are wirelessly connected to themonitoring system, and a user associated with a HUD device may beinterested in determining the strength of a wireless network at variouslocations of a property. For example, an installer may desire to installone or more cameras, sensors, or other components in the monitoringsystem 200, where the cameras, sensors, or other components wirelesslycommunicate with the monitoring system 200. For example, the cameras,sensors, or other components may communicate with the monitoring controlunit 210 via the module 230 over a wireless area network (WAN) or localarea network (LAN), such as a Wi-Fi network, Bluetooth connection,Z-Wave network, or ZigBee network. To determine where the cameras,sensors, or other components can be placed at the property, an installerequipped with the HUD device 250 may be provided with information in theHUD that indicates the network strength at the location of the installer(e.g., when the HUD device 250 is a wearable electronic device that theinstaller is wearing). Based on the installer being presented withinformation at the HUD device 250 that indicates the network signalstrength, the installer can identify preferred locations for theplacement of the one or more cameras, sensors, or other components aswell as locations where the cameras, sensors, or other components areunable to communicate with the monitoring system 200. In some instances,the monitoring system 200 may utilize two or more different networks(e.g., a Wi-Fi network and a Z-Wave network) to communicate withcomponents of the monitoring system 200, and the HUD device 250 maypresent indications of signal strength for one or more of the differentnetworks.

In some implementations, data related to configuring or performingtesting of cameras, sensors, or other components of a monitoring system,or for determining network signal strength in a monitoring systemnetwork, can be pushed from a local source, such as a control panel ofthe monitoring system or other local component. For example, aninstaller equipped with a HUD device 250 may provide input at the HUDdevice 250 to initiate a test of a new sensor installed in themonitoring system 200, and the monitoring control unit 210 may transmitdata to the sensor to perform the test. Based on receiving the resultsof the test, the monitoring control unit 210 may transmit data to theHUD device 250 that includes information indicating whether the test wassuccessful. In some implementations, additional information can betransmitted to the HUD device 250 in addition to the results of thetest, for example, instructions indicating how the installer canreconfigure the sensor to resolve errors identified by the test. Similartechniques can be utilized to provide the HUD device 250 with data feedsfrom various cameras, sensors, or other components associated with themonitoring system 200, for example, by first receiving video feed dataat the monitoring control unit 210 and subsequently relaying the videofeed data to the HUD device 250.

In other implementations, data related to configuring or performingtests of components of a monitoring system may be sourced remotely, forexample, from a server or other cloud computing source. For instance, aninstaller equipped with a HUD device 250 may use the HUD device 250 toinitiate a test of a new sensor installed in the monitoring system 200,and the monitoring application server 260 may transmit data to themonitoring control unit 210 and/or other components of the monitoringsystem 200 to perform the test requested by the installer. Subsequently,the monitoring control unit 210 or another component of the monitoringsystem 200 may transmit data relating to the test to the monitoringapplication server 260 (e.g., data confirming that the test request hasbeen received by the component or data reporting the results of thetest). The monitoring application server 260 can receive the informationand can relay some or all of the received information to the HUD device250. Similar techniques can be utilized to provide data feeds fromvarious cameras, sensors, or other components associated with themonitoring system 200, for example, by first transmitting video feeddata to the monitoring application server 260 and then relaying the datato the HUD device 250.

In some implementations, configuring a camera, sensor, or othercomponent of a monitoring system may require that the monitoring systembe in a particular state. For example, a particular test performed on acamera, sensor, or other component of a monitoring system may requirethat the monitoring system be either in an armed on unarmed state priorto performing the test. To facilitate an installer in performing thetest, the installer may be able to provide input at a device featuring aHUD to control the monitoring system. For example, an installer who isequipped with a HUD device 250 and installing or configuring a videocamera to operate with the monitoring system 200 may require that themonitoring system 200 is in an unarmed state during a particular portionof the installation or configuration process. The installer may be ableto provide input at the HUD device 250 that temporarily disarms themonitoring system 200 while the installation or configuration process isperformed, and may provide additional input at the HUD device 250 torearm the monitoring system 200 after the installation or configurationis complete.

Similarly, in instances in which an installer is installing orconfiguring a camera, sensor, or other component of a monitoring system,it may be necessary to trigger one or more alarms at a propertyassociated with the monitoring system to validate that the camera,sensor, or component is functioning properly. In these situations, theinstaller may be able to temporarily deactivate the triggering of alarmsby the monitoring system, or to deactivate the reporting of alarms tocertain users or other recipients. For example, while configuring ortesting a door sensor at a property, it may be necessary to simulate anevent in which an intruder enters the property by opening the doorassociated with the sensor while the door is locked and the monitoringsystem 200 is armed. In order to avoid alerting other users associatedwith the property with a false intruder alarm generated while performingthe sensor test, an installer equipped with a HUD device 250 may provideinput at the HUD device 250 that temporarily deactivates thetransmission of alarms to other users of the property. In someimplementations, the installer may be able to deactivate alarmsassociated particular alarm events. For example, an installer may beable to deactivate alarms relating to intruder alerts, but may be ablemaintain alarm settings for notifying users of fires detected at theproperty. In some implementations, the installer may be able todeactivate alarms from being transmitted to certain users or certaingroups of users. For instance, while the installer is testing a doorsensor of a property associated with the monitoring system 200, theinstaller may provide input at the HUD device 250 that temporarilysuspends notifications from being transmitted to emergency responders(e.g., police departments, fire departments, emergency medical services,etc.) while continuing to send notifications to other users of theproperty.

As described, in some implementations, a device featuring a heads-updisplay (HUD) may be feature a camera capable to obtain images and/orvideo from the environment of a user. For example, an installer or userof a property may be equipped with a wearable electronic device thatfeatures a HUD and that is associated with a monitoring system of aproperty, and the HUD device may capture images or video that includesthe field of view the user or installer as they move about the property.In some implementations, images or video may be captured from the HUDdevice continuously, periodically, based on the detection of aparticular event, or based on user input triggering the capture ofimages or video. In some implementations, the monitoring system canperform analysis of the images or video captured by the camera of theHUD device to identify actions to perform. The monitoring system mayalso store the images or video captured by the HUD device, or maytransmit the images or video to another recipient over one or morenetworks.

In some implementations, images and/or video of a property can be usedto generate maps of the property. For example, analyzing images or videomay be used to generate maps that may include information defining thelayout of the property, the location of various sensors, devices, orappliances within the property, locations where users of the propertyare likely to be located within the property (e.g., by identifyingparticular rooms as bedrooms), etc. Such maps may be two-dimensional(2D) models or maps of a property, or may be three-dimensional (3D)models or maps of a property.

In some implementations, images or videos of a property can be used todetermine and track an inventory of the property. For example, themonitoring system may have access to information identifying variouscameras, sensors, and other components of the monitoring system, andthis information may be analyzed in the context of a property map toidentify the locations of the cameras, sensors, or other components ofthe monitoring system within the property. The monitoring system canstore an inventory of the various monitoring system components and theirlocations within the property. Additionally, image or video dataobtained from the camera of a HUD device may enable the cataloging ofother items within a property. For example, images or video of valuableitems in a property may be stored for later use in the event that aninsurance claim or recovery must be made with regards to the items. Insome implementations, information defining maps of a property,information cataloging various items within a property, and inventoriesof monitoring system components and their respective locations may becollectively stored by the monitoring system. For example, themonitoring system 200 may maintain a “vault” of images, videos, maps,inventories, and other information associated with the property (e.g.,logs and models of monitoring system control panel usage, performancelogs and models for thermostats or other HVAC system components, etc.).

In some implementations, images or video obtained by a camera of a HUDdevice associated with a user may be transmitted to other recipients. Insome instances, these images or videos are transmitted to the otherrecipients based on certain events being detected at the property. Forinstance, based on determining that an emergency is taking place at theproperty, the monitoring system associated with the property maytransmit image or video data obtained by a HUD device to properauthorities. In some implementations, images or video can be obtained bythe camera of the HUD device and transmitted to other recipients in nearreal time. As an example, if the monitoring system 200 detects a fire ata property, live video from one or more HUD devices 250 or other camerasassociated with the monitoring system 200 may provide live video feedsto first responders, such as fire fighters or paramedics, to assist thefirst responders in locating the source of the fire, the locations ofusers within the property, etc.

In another example, images or video obtained by a camera of a HUD deviceassociated with a user who is installing or configuring a component ofthe monitoring system may be transmitted to a recipient who is a remoteinstaller. A local installer who is in the same physical location as themonitoring system component and who is equipped with the HUD device canutilize a camera of the HUD device to obtain video or images of theinstallation or configuration process that the installer is engaged in,and can send the video or images to the remote installer. In this way,the remote installer is provided with a view of the actual installationor configuration process that the local installer is engaged in. Theremote installer receives the video or images, and can use the video orimages in determining how to install or configure the monitoring systemcomponent. The remote installer may then provide the local installer whois in the same physical location as the monitoring system component withinformation that informs the local installer how to install or configurethe monitoring system component. For example, the remote installer maybe able to annotate images or video, provide diagrams, or provide otherinformation or feedback that can then be presented visually to the localinstaller in the HUD device.

For instance, the remote installer may annotate an image of themonitoring system component that the local installer is installing orconfiguring to include information (e.g., arrows, words, etc.) that canbe presented to the local installer in the heads-up display of the HUDdevice. The local installer can view this information while performingthe installation or configuration to aid in performing these tasks. Insome instances, the local installer may be provided with informationfrom the remote installer and other information obtained by themonitoring system component that they are installing or configuring. Forinstance, an installer who is configuring a camera and is located in thesame location as the camera can be presented information in the HUDdevice that includes both an annotated image received from a remoteinstaller and a video feed obtained by the camera that the installer isconfiguring.

In some implementations, information determined based on the analysis ofimages or video obtained by a camera of a HUD device and stored by themonitoring system can be transmitted to other recipients, based ondetecting certain events at a property. As an example, if a fire isdetected by a particular smoke detector associated with the monitoringsystem of a property, the monitoring system can automatically notify afire department of the emergency, and can further provide the firedepartment with map data detailing the location of the smoke detectorthat detected the fire at the property. This additional information mayenable first responders to better navigate the property and to moreefficiently locate the source of an alarm.

In some implementations, images captured by a HUD device or other cameraof a monitoring system can be used to provide additional capabilities toa monitoring system. For instance, images of occupants or pets of aproperty may be obtained by a HUD device or other camera and used toperform visual verification of people or animals entering or exiting aproperty. Such visual analysis may assist in determining whether analarm triggered at the property is due to an intruder or due to anoperator error (e.g., neglecting to disarm the property's monitoringsystem prior to entering the property). Similarly, images of pets may beused to tune a monitoring system's pet immunity or other sensitivitysettings to avoid false alarms caused by the movements of pets at theproperty.

Other applications associated with the configuration and use of aproperty monitoring system may utilize information received from,transmitted to, or obtained by a device featuring a heads-up display.Many of such applications utilize wearable electronic devices associatedwith one or more users of a property, where the wearable electronicdevices may feature heads-up displays.

In some implementations of the described subject matter, a cameraassociated with a HUD device may be used as a scanner device that iscapable of identifying a component of a monitoring system by scanning abarcode associated with the component. The component can be enrolled inthe monitoring system based on the information encoded in the bar code.

Enrolling devices using barcodes can enable installers or other users ofa property to associate a particular component with a monitoring systemeven when they are not located near the monitoring system. For example,an installer may have a HUD device featuring a camera or other cameradevice, and the installer may be able to scan a barcode on a componentor component package to register the component with the monitoringsystem. In some instances, the installer may be able to register thecomponent with the monitoring by designating a name of the component inaddition to providing information encoded in a barcode (e.g., inaddition to the data encoded in the barcode scanned using the HUDdevice). In some implementations, barcodes of third-party components,such as a garage door controller, furnace, etc., may be scanned by theinstaller to associate the third-party component with the monitoringsystem. Such an implementation may enable, for example, an installer toregister the third-party device with a monitoring system network, suchas the network 205.

In other implementations, an installer can increase the efficiency andreliability of performing monitoring system installation by registeringcomponents of the monitoring system via barcode scanning. For example,prior to installation, an installer may scan a barcode of each componentto be installed in the monitoring system, and optionally may designate aname or location associated with the component. Subsequently, when theinstaller is installing the one or more components, the installer may beable to scan the barcode of a particular component again to be presentedwith information that indicates where the component should be installedin the property, how the component should be configured to functionwithin the monitoring system, etc. In some implementations, an installermay be able to replace an existing component of a monitoring system byscanning the barcode of the replacement component and/or the barcode ofthe component to be replaced, where scanning the barcodes may insert thereplacement component in the monitoring system in the place of thereplaced component.

In some implementations, the application operating on the HUD device mayenable users of the monitoring system to initialize a networkrediscovery process, or to add or delete components to the monitoringsystem network. For example, if the monitoring system 200 utilizes aZ-Wave network as the network 205, the native control application 252associated with the HUD device 250 may enable a user to add or deletecomponents from the monitoring system's network 205, or may enable theuser to instruct the monitoring system 200 to perform a networkrediscovery process.

In some applications, data obtained by a HUD device or other cameradevices associated with a property may be useful for designating andtuning entry and exit delay times associated with a property'smonitoring system. For example, an exit or entry delay time mayrepresent the amount of buffer time that the monitoring system providesusers to set their alarm system and then exit the property beforedetecting an alarm event, or to enter the property and disarm the alarmsystem before detecting an alarm event. Based on image or video dataobtained by a HUD device camera or other camera, the exit and entrydelay times associated with a property may be adjusted to setappropriate lengths of entry and exit buffer times, to avoid falsealarms at the property while maintaining effective monitoring. In someinstances, an installer of a monitoring system may use a HUD device orother device to determine entry and exit times while they are installingthe monitoring system. For example, the installer may simulate usersexiting or entering the property, and may record the time taken toperform these actions via the HUD device or other camera. In someinstances, determining the exit and entry times associated with aproperty may involve other data, for example, timestamps that indicatewhen a user has armed or disarmed the monitoring system, or timestampsthat indicate when the user has provided voice commands at a HUD devicethat indicate when they have arrived or exited a property. Based on theimage data and/or the timestamps, entry and exit times may be configuredfor the monitoring system. In some instances, multiple exit and entrytimes can be associated with a particular property. For example, aproperty may be associated with different exit and entry times dependingupon which monitoring system control panel a user uses to arm or disarma monitoring system, depending upon which exit or entrance the userutilizes, etc.

The use of a HUD device or other camera device may further enableinstallers to tune the sensitivity of a property monitoring system bydesignating triggering areas that should be particularly sensitive orparticularly tolerant of conditions that might trigger an alarm. Forexample, an installer having a HUD device may perform a walk-through ofa property, and may designate certain areas, such as a foyer or otherhigh-traffic areas of a property, to be particularly tolerant ofmovements or noises that might inadvertently trigger an alarm.Similarly, the installer may designate other zones of the property assensitive zones where alarms may be triggered more easily. For example,a basement area that is used infrequently by the users of a property maybe more sensitive to movements that would trigger an alarm, so as toeffectively detect potential intruders in the property. In someinstances, an installer of a property may verify monitoring systemsensitivity settings by performing a walk-through of a property andbeing presented with information in HUD device that indicates whetherparticular sensors of the monitoring system are detecting alarm events,where the installer may then further adjust the sensitivity ofparticular sensors or sensors associated with particular zones of theproperty.

In some implementations, users of a property who are equipped with a HUDdevice can provide input at the HUD device to indicate whether detectedevents at a property are emergency or duress events. For example, a usermay be able to speak a certain command, provide a particular gesture,perform a certain eye movement, or provide other input at a HUD deviceto indicate that a particular alarm is associated with an emergency. Forinstance, if a smoke detector at a property is triggered, a user havinga HUD device may be able to provide input at the HUD device to indicatethat the triggering of the smoke detector is an emergency (e.g., thatthe smoke detector was triggered by a fire at the property and notsomeone cooking at the property).

In some instances, a user having a HUD device can use informationcaptured by the HUD device to generate a sales quote for a homemonitoring system, or other product or service associated with aproperty. For instance, an installer or sales associate equipped with aHUD device may perform a walk-through of a property, and a camera of theHUD device may capture images or video that can be analyzed to generatea quote for a particular product or service for the home. For instance,a quote sheet can be generated that indicates where monitoring systemcameras, sensors, or other components should be placed in a property toachieve proper monitoring of the property, and the quote sheet can beprovided to users to aid their purchasing process. In some instances,sales associates can include other information with the sales quote viathe HUD device, or can make additional notes that may aid an installervia the HUD device. For example, information suggesting possibleupgrades to the monitoring system, images of users or pets of theproperty to be used for setting a monitoring system's visualverification settings, etc., can be input using a HUD device andincluded in a sales quote or other document produced in conjunction witha sales process. While described herein with respect to generating salesquotes for property monitoring systems, similar techniques areapplicable for generating other sales quotes or information relating toother sales, for example, carpet sales, appliance or HVAC systeminstallation, cable routing, plumbing installation, room painting, etc.

FIG. 3 depicts a flow chart of an example process 300 that assists aninstaller or other user with the configuration of a monitoring systemcomponent. The process 300 assists with the configuration process byproviding an installer of the monitoring system component withinformation from or related to the monitoring system component beinginstalled in a heads-up display device that the installer is wearing.The installer can view this information in the heads-up display whilemaintaining use of both of their hands as they configure the monitoringsystem component. Maintaining use of both hands during the installationprocess also increases the safety of the installation process,especially in instances where the installer is performing theinstallation in a dangerous area, such as a top a ladder or on the roofof a property. In some implementations, the process 300 can be performedby the system 200 of FIG. 2. For example, the steps of the process 300can be performed by the monitoring control unit 210 and/or themonitoring application server 260 associated with the monitoring system200.

Data identifying a component of the monitoring system is received from awearable electronic device that is associated with the monitoring system(302). For example, an installer wearing the HUD device 250 can provideinput to the HUD device 250 that identifies a component 230 of themonitoring system that the installer is configuring. In someimplementations, as described, the installer may also specify specificinformation that they are interested in receiving from or relating tothe component 230 of the monitoring system that the installer isconfiguring. For example, an installer may request to receive sensordata obtained by the component 230, such as a temperature detected by atemperature sensor, or may request to receive test data for thecomponent 230, such as data indicating whether a test of the temperaturesensor was successful.

The monitoring system accesses monitoring system data collected by thecomponent of the monitoring system that is identified by the datareceived from the wearable electronic device. For example, themonitoring control unit 210 can receive information identifying a cameracomponent of the monitoring system 200, and can access video dataobtained by the camera component of the monitoring system 200. In otherexamples, the monitoring system data collected by the component 230 ofthe monitoring system 200 may be sensor data collected by one or moresensors of the monitoring system 200, such as temperature data from aparticular temperature sensor, audio data from a microphone or othernoise sensor, humidity data from a humidity sensor, motion detectiondata collected by a motion or knock sensor, etc.

Additionally, in some instances the monitoring system data collected bythe identified component 230 of the monitoring system 200 may be datathat is not specifically related to the sensing or detection functionsof the identified monitoring system component 230 but is related to theoverall functionality of the identified monitoring system component 230.For example, the monitoring control unit 210 may access informationcollected by the identified component 230 of the monitoring system 200that indicates the strength of a wireless network signal detected by theidentified component 230, may be data that indicates the current stateof a battery of the identified component 230 of the monitoring system200, etc.

In some instances, depending upon the information received from orrelated to the identified component 230 of the monitoring system 200,the monitoring control unit 210, the monitoring application server 260,or another component of the monitoring system 200 may perform ananalysis of the accessed monitoring system data collected by theidentified component 230 of the monitoring system 200. For example,temperature sensor data obtained by a temperature sensor of themonitoring system 200 may be analyzed to determine whether thetemperature data obtained by the temperature sensor is consistent withtemperature data obtained by other temperature sensors associated withthe monitoring system 200 or is consistent with a weather forecast forthe geographical region of the property associated with the monitoringsystem 200. Similarly, if the monitoring system 200 is performing a testof the identified component 230, the monitoring system 200 may analyzemonitoring system data obtained by the identified component 230 todetermine whether the accessed data satisfies the test.

At least a portion of the monitoring system data collected by thecomponent of the monitoring system is provided to the wearableelectronic device for display at a heads-up display of the wearableelectronic device. (306) For example, based on accessing the monitoringsystem data collected by the component 230 of the monitoring system 200,the monitoring control unit 210 of the monitoring system 200 cantransmit at least a portion of the monitoring system data to the HUDdevice 250 for presentation at the heads-up display of the HUD device250. The monitoring system data provided to the HUD device 250 can beoutput to an installer wearing the HUD device 250 such that theinstaller may be able to view the monitoring system data and rely on themonitoring system data in configuring the component 230 of themonitoring system 200. For example, the monitoring control unit 210 canreceive a video feed from a camera component of the monitoring systemand can present the video feed at the heads-up display of the HUD device250. The installer wearing the HUD device 250 can adjust the field ofview of the camera component, viewing the effects of their adjustmentsin the heads-up display of the HUD device 250, until the cameracomponent is configured to have the appropriate field of view for thearea of the property that the camera component is designated to monitor.

In some examples, the information provided for output at the heads-updisplay of the HUD device 250 can include results of an analysis of themonitoring system data obtained by the component 230 of the monitoringsystem 200. For example, based on the monitoring control unit 210analyzing monitoring system data obtained by a component 230 of themonitoring system 200 to determine whether the component 230 isoperating properly or passes a functionality test, the monitoringcontrol unit 210 can provide at least a portion of the results of thatanalysis for presentation at the heads-up display of the HUD device 250.

FIG. 4 depicts an example system 400 that is capable of assisting withthe configuration of a component of a monitoring system. In the examplesystem 400, data obtained from multiple components of the monitoringsystem is presented at a heads-up display of a wearable electronicdevice that is being worn by an installer of the monitoring systemcomponent. For example, as shown in FIG. 4, an installer 402 may beinstalling one or a pair of cameras 430 a, 430 b and configuring thecameras 430 a, 430 b to monitor an area of a property. The installer maydesire to view the fields of view 435 a, 435 b of each of the cameras430 a, 430 b while configuring the cameras 430 a, 430 b to ensure thatthere is not a “blind spot” in the fields of view 435 a, 435 b in thearea being monitored by the cameras 430 a, 430 b.

To allow for configuration of the cameras 430 a, 430 b such that thefields of view 435 a, 435 b will not result in a “blind spot” in thearea monitored by the cameras 430 a, 430 b, the installer 402 canprovide input to their wearable electronic device 450 that includes aheads-up display 452. The input provided by the installer 402 canidentify each of the cameras 430 a, 430 b, and may also identifyinformation that the installer 402 is requesting from or relating to thecameras 430 a, 430 b. For instance, the installer 402 can provide inputto the wearable electronic device 402 that identifies the cameras 430 a,430 b and further indicates that the installer 402 would like to see thefields of view 435 a, 435 b of each of the cameras 430 a, 430 b.

The request input by the installer is transmitted from the wearableelectronic device 450 to a monitoring system control unit 410 (Step A).The monitoring system control unit 410, similar to the monitoring systemcontrol unit of FIG. 1, includes one or more control panels, servers, orother computing systems. The wearable electronic device 450 may transmitthe request that identifies at least the cameras 430 a, 430 b over oneor more wireless networks over which the wearable electronic device 450and the monitoring system control unit 410 are in communication.

The monitoring system control unit 410 receives the request from thewearable electronic device that identifies the cameras 430 a, 430 b, andrequests information from the cameras 430 a, 430 b in response toreceiving the request (Step B). For example, based on the monitoringsystem control unit 410 receiving the data from the wearable electronicdevice 450 that identifies the cameras 430 a, 430 b, the monitoringsystem control unit 410 can request video data of the cameras' fields ofview 435 a, 435 b by transmitting a separate request to each of thecameras 430 a, 430 b that requests video data from the cameras 430 a,430 b. Alternatively, the monitoring system control unit 410 cantransmit a single request to components of the monitoring system,including the cameras 430 a, 430 b that requests the video data obtainedby the cameras 430 a, 430 b.

Each of the cameras 430 a, 430 b can receive the request from themonitoring system control unit 410, and can reply to the request bytransmitting the requested data to the monitoring system control unit410 (Step C). For example, each of the cameras 430 a, 430 b can receivea request to transmit video data to the monitoring system control unit410, and can each reply to the request by transmitting video data or aportion of video data to the monitoring system control unit 410.

In some instances, the cameras 430 a, 430 b do not require a requestfrom the monitoring system control unit 410 to transmit the video datato the monitoring system control unit 410. Rather, the cameras 430 a,430 b may automatically transmit the video data to the monitoring systemcontrol unit 410, such that the monitoring system control unit 410 wouldnot be required to request the video data from the cameras 430 a, 430 b,but rather would have already received or already be receiving the videodata. In other instances, if the monitoring system control unit 410requests only a portion of the video data obtained by the cameras 430 a,430 b, or particular frames, such as every 10^(th) frame, of videoobtained by the cameras 430 a, 430 b, the cameras 430 a, 430 b mayrespond to the request by transmitting the requested information to themonitoring system control unit 410.

The monitoring system control unit 410 receives the video data from eachof the cameras 430 a, 430 b, and provides at least a portion of thevideo data obtained from each of the video cameras 430 a, 430 b to thewearable electronic device 450 for display at the wearable electronicdevice 450 (Step D). For example, based on receiving the video data fromeach of the cameras 430 a, 430 b, the monitoring system control unit 410can combine at least a portion of the video data received from each ofthe cameras 430 a, 430 b, and can transmit the data to the wearableelectronic device 450. The wearable electronic device 450 can receivethe video data and can display the video data received from one of thecameras 430 a in a first region 454 a of the wearable electronicdevice's heads-up display 452, and can display video data received fromthe other camera 430 b in a second region 454 b of the wearableelectronic device's heads-up display 452.

In some implementations, the monitoring system control unit 410 receivesthe video data from the cameras 430 a, 430 b and processes the videodata from the cameras 430 a, 430 b to merge the video data received fromthe cameras 430 a, 430 b into a single segment of video data thatincludes the video from both cameras 430 a, 430 b in a single videofile. For example, the monitoring system control unit 410 can processthe video data received from each of the cameras 430 a, 430 b togenerate a single video file that includes the video from the cameras430 a, 430 b side-by-side as shown in the heads-up display 452 of thewearable electronic device 450.

Alternatively, the monitoring system control unit 410 may receive thevideo data from the cameras 430 a, 430 b and transmit the video data ora portion of the video data received from the cameras 430 a, 430 b tothe wearable electronic device 450 without performing additionalprocessing on the video data. The wearable electronic device 450 mayreceive the video data that was obtained from each of the cameras 430 a,430 b and may present the video data obtained from each of the cameras430 a, 430 b side-by-side in the heads-up display 452 of the wearableelectronic device 450.

While shown in FIG. 4 as being presented in a side-by-side fashion, withthe video data from one camera 430 a being presented in a first region454 a of the heads-up display 452 and the video data from the othercamera 430 b being presented in a second region 454 b of the heads-updisplay 452, in other implementations the data or portions of the videodata obtained from the cameras 430 a, 430 b may be presented in otherways. For example, the video data may be presented such that the videopresented in the heads-up display 452 alternates between the video dataobtained from a first camera 430 a and the video data obtained from asecond camera 430 b. The video data from one camera 430 a may bepresented above or below the video data from the other camera 430 b inthe heads-up display 452. Other methods of presenting the video dataobtained from each of the cameras 430 a, 430 b may be utilized, with theresult being that the installer 402 viewing the heads-up display 452 isable to comprehend each of the fields of view 435 a, 435 b of thecameras 430 a, 430 b, thereby enabling the installer 402 to configurethe fields of view 435 a, 435 b of the cameras 430 a, 430 b to ensurethere are no “blind spots” in the area to be monitored by the cameras430 a, 430 b.

While discussed with respect to video data obtained from cameras 430 a,430 b, in other implementations the process of FIG. 4 may enable aninstaller to view data obtained by two or more other components of amonitoring system simultaneously or to alternate between viewing dataobtained by two or more other components of the monitoring system. Forexample, the installer 402 may request data from two differenttemperature sensors that are associated with the monitoring system, andmay be presented with information obtained by the two temperaturesensors simultaneously in the heads-up display 452 of the wearableelectronic device 450.

In other examples, the installer 402 may request to view informationobtained by two different types of monitoring system componentssimultaneously. For example, to confirm whether a door sensor isfunctional, the installer 402 may request to view data obtained by thedoor sensor and at the same time to view video data obtained by a camerathat has a view of the door that the door sensor is associated with. Theinstaller 402 may be presented, at the heads-up display 452, withinformation from both the door sensor and the camera, to determine, forexample, whether the door sensor properly detects the door being openedwhen the installer 402 is able to see that the door has been opened fromthe video data.

Additionally, while described with respect to FIG. 4 as including datafrom two components of the monitoring system, in other implementationsthe installer 402 may request monitoring system data obtained by morethan two components of the monitoring system. In such an instance, themonitoring system control unit 410 may receive the monitoring systemdata obtained by the components of the monitoring system and present themonitoring system data in the heads-up display 452 in a similar fashionas discussed with respect to FIG. 4.

FIGS. 5A and 5B illustrate an example of a system that assists with theconfiguration of monitoring system components by enabling the remotetesting of monitoring system components. In some examples, whileconfiguring a component of a monitoring system, an installer of thecomponent may need or want to test the component. If the component islocated in a hard to reach area or is remote from a control panel of themonitoring system, the installer may not be able to properly test thecomponent, or may be inconvenienced by having to move between a controlpanel of the monitoring system and the component while performing thetest. However, when the installer can activate or control the monitoringsystem and testing of the component using a wearable electronic device,the installer may be able to more effectively or efficiently test thecomponent being installed and/or configured.

For example, as shown in FIG. 5A, a system 500 includes a wearableelectronic device 550 that is being worn by an installer 502, amonitoring system control unit 510, and one or more monitoring systemcomponents 530 a-530 n, including the component 530 i that the installer502 is configuring. While installing and configuring the component 530i, the installer 502 may desire to test the component that they areinstalling. In some instances, testing the component may require placingthe monitoring system or one or more components of the monitoring systemin a particular state. For example, the component 530 i may be athermostat fan that is configured to automatically turn off in responseto a smoke detector detecting the presence of a possible fire. Testingof the thermostat fan may require that the monitoring system is in aparticular state, such as a state that the monitoring system enters whenthe smoke detector detects the presence of a possible fire. Performingtesting of the thermostat fan may also require the monitoring system tobe in additional, or different states for additional, or differentdiagnostic tests.

To perform testing of the component 530 i, the installer 502 may providean input to their wearable electronic device 550 that specifies aparticular system state that the monitoring system should be in whilethe test is performed. The request for the particular system state maybe transmitted to the monitoring system control unit 510 by the wearableelectronic device 550 (Step A). The monitoring system control unit 510can receive the data specifying the system state, and may control themonitoring system to enter the system state (Step B). For example, themonitoring system control unit 510 may transmit data to one or more ofthe monitoring system components 530 a-530 n to place the monitoringsystem into the requested state. Placing the monitoring system into therequested state may involve placing one or more of the monitoring systemcomponents 530 a-530 n into specific states and/or may involve adjustingother parameters associated with the monitoring system, such asdetection tolerances maintained by the monitoring system control unit510 and used to determine whether specific events have occurred at theproperty being monitored by the monitoring system. For example, themonitoring system may enter a state associated with the monitoringsystem's smoke detector having detected the presence of a possible fire,or a smoke detector component of the monitoring system may be placed ina state associated with the smoke detector detecting the presence of apossible fire.

After the monitoring system has been configured to the appropriatestate, the installer 502 may request a test of the particular component530 i of the monitoring system (State C). For example, the installer 502may provide input at the wearable electronic device 550 that requestsinitialization of the testing of the particular component 530 i, such asthe thermostat fan that the installer 502 is configuring to operate withthe monitoring system. The request for the testing of the monitoringsystem component 530 i can be received at the monitoring system controlunit 510, and the monitoring system control unit 510 can control theparticular monitoring system component 530 i to initialize the testingof the component 530 i (Step D). For example, the monitoring systemcontrol unit 510 may transmit information to the monitoring systemcomponent 530 i that initializes testing of the component 530 i.

The monitoring system component 530 i being tested can transmit testresult data to the monitoring system control unit 510 as a part of itstesting (Step E). For example, the monitoring system component 530 ithat is a thermostat fan can transmit data to the monitoring systemcontrol unit 510 that indicates whether the thermostat fan hasautomatically shut off in response to a test in which the monitoringsystem simulates a smoke detector detecting a possible fire. Whiledescribed in the present example as data indicating whether thethermostat fan has deactivated in response to the test, other sensors,cameras, or other components of the monitoring system may gatherdifferent monitoring system data. This data is provided to themonitoring system control unit 510 for analysis by the monitoring systemcontrol unit 510, for example, to determine whether a specific event hastaken place at the property or whether a specific component has passed adiagnostic test initiated by an installer 502.

The monitoring system control unit 510 analyzes the test result dataobtained from the component 530 i to determine whether the component 530i has passed or failed the test (Step F). For example, the monitoringsystem control unit 510 may analyze the monitoring system data receivedfrom the component 530 i to determine whether the component 530 i hasresponded as expected to the test. As shown in FIG. 5A, the analysis ofthe data received from the monitoring system component 530 i indicatesthat the test was successful, and so the monitoring system control unitprovides information for display at the heads-up display 552 of thewearable electronic device 550 that indicates that the test wassuccessful (Step G).

For example, as shown in FIG. 5A, the heads-up display 552 of thewearable electronic device 550 may display an indication that thetesting of the component 530 i was successful. The heads-up display 552may further include other information relating to the testing of thecomponent 530 i, for example, the indication that the monitoring systemwas in state “A” for the test of the component 530 i, that the component530 i that is a thermostat fan properly deactivated during the test, andthat the monitoring system at the time of the test included the activecomponents 530 a-530 n.

FIG. 5B illustrates a similar example, but shows information that may bedisplayed to the installer 502 at the heads-up display 552 of thewearable electronic device 550 if the test of the component 530 i isunsuccessful. When the monitoring system control unit 510 receives datafrom the component 530 i in response to the monitoring system controlunit 510 initializing a test of the component 530 i, the monitoringsystem control unit 510 may perform an analysis of the data anddetermine that the component 530 i has failed the test (Step F). Forexample, the monitoring system control unit 510 may analyze the datareceived from the thermostat fan and determine that the data receivedfrom the thermostat fan does not correspond to the anticipated responsefor the test. For instance, even though the monitoring system may be ina state in which a smoke detector of the monitoring system has detecteda possible fire, the monitoring system control unit 510 may receive datafrom the thermostat fan indicating that the fan is still active, when infact it should deactivate in response to the monitoring system receivingdata from the smoke detector that indicates a possible fire. Based on ananalysis of the data received from the component 530 i, the monitoringsystem control unit 510 may determine that the component 530 i hasfailed the test requested by the installer 502.

Additionally, based on determining that the component 530 i has failedthe test requested by the installer 502, monitoring system control unit510 may determine additional information relating to the failure of thetest or to configuring the component 530 i to pass the test. Forexample, the monitoring system control unit 510 may analyze the datareceived from the component 530 i and may determine an error that led tothe component 530 i failing the test. Additionally or alternatively, themonitoring system control unit 510 may determine one or more steps orpotential solutions that the installer 502 may utilize in an attempt toconfigure the component 530 i to pass the test.

The monitoring system control unit 510 can transmit data to the wearableelectronic device 550 for display at the heads-up display 552 of thewearable electronic device, where the information to be displayedincludes an indication that the component 530 i has failed the test andincludes the troubleshooting data related to configuring the component530 i to potentially pass the test. For example, as shown at FIG. 5B,the heads-up display 552 of the wearable electronic device 550 caninclude an indication that the test of the thermostat fan has failed andan indication of the possible troubleshooting measures that theinstaller 502 can take with respect to the thermostat fan to configurethe thermostat fan to pass the test, namely to “restart the device,”“initialize network rediscovery,” or “send test communication fromthermostat control panel.”

The described systems, methods, and techniques may be implemented indigital electronic circuitry, computer hardware, firmware, software, orin combinations of these elements. Apparatus implementing thesetechniques can include appropriate input and output devices, a computerprocessor, and a computer program product tangibly embodied in amachine-readable storage device for execution by a programmableprocessor. A process implementing these techniques can be performed by aprogrammable processor executing a program of instructions to performdesired functions by operating on input data and generating appropriateoutput. The techniques can be implemented in one or more computerprograms that are executable on a programmable system including at leastone programmable processor coupled to receive data and instructionsfrom, and to transmit data and instructions to, a data storage system,at least one input device, and at least one output device. Each computerprogram can be implemented in a high-level procedural or object-orientedprogramming language, or in assembly or machine language if desired; andin any case, the language can be a compiled or interpreted language.Suitable processors include, by way of example, both general and specialpurpose microprocessors. Generally, a processor will receiveinstructions and data from a read-only memory and/or a random accessmemory. Storage devices suitable for tangibly embodying computer programinstructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, such asErasable Programmable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), and flash memory devices;magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Anyof the foregoing can be supplemented by, or incorporated in, speciallydesigned application-specific integrated circuits (ASICs).

It will be understood that various modifications can be made. Forexample, other useful implementations could be achieved if steps of thedisclosed techniques were performed in a different order and/or ifcomponents in the disclosed systems were combined in a different mannerand/or replaced or supplemented by other components. Accordingly, otherimplementations are within the scope of the disclosure.

What is claimed is:
 1. An electronic system comprising: at least oneprocessor; and at least one computer-readable medium coupled to the atleast one processor having stored thereon instructions which, whenexecuted by the at least one processor, causes the at least oneprocessor to perform operations comprising: receiving data identifying acomponent of a monitoring system from a wearable electronic device thatis associated with the monitoring system, wherein the monitoring systemis associated with a property and includes components that are fixedwithin the property and that are configured to sense attributes of theproperty, and wherein the wearable electronic device includes a heads-updisplay and communicates with the monitoring system over a wirelessnetwork; accessing, based on the data identifying the component of themonitoring system, monitoring system data collected by the component ofthe monitoring system; and providing, to the wearable electronic devicefor display at the heads-up display of the wearable electronic device,at least a portion of the monitoring system data collected by thecomponent of the monitoring system.
 2. The electronic system of claim 1,wherein the component of the monitoring system is a camera associatedwith the monitoring system, and wherein: accessing monitoring systemdata collected by the component of the monitoring system comprisesaccessing video or image data collected by the camera associated withthe monitoring system; and providing at least a portion of themonitoring system data collected by the component of the monitoringsystem comprises providing at least a portion of the video or image datacollected by the camera associated with the monitoring system to thewearable electronic device for display at the heads-up display of thewearable electronic device.
 3. The electronic device of claim 1, whereinthe component of the monitoring system is a sensor associated with themonitoring system, and wherein: accessing monitoring system datacollected by the component of the monitoring system comprises accessingsensor data collected by the sensor associated with the monitoringsystem; and providing at least a portion of the monitoring system datacollected by the component of the monitoring system comprises providingat least a portion of the sensor data collected by the sensor associatedwith the monitoring system to the wearable electronic device for displayat the heads-up display of the wearable electronic device.
 4. Theelectronic system of claim 1, wherein the operations comprise:determining a data transfer rate between the wearable electronic deviceand the monitoring system that communicate over the wireless network;selecting, based on the data transfer rate between the wearableelectronic device and the monitoring system that communicate over thewireless network, a portion of the monitoring system data collected bythe component of the monitoring system; and providing, to the wearableelectronic device for display at the heads-up display of the wearableelectronic device, the selected portion of the monitoring system datacollected by the component of the monitoring system.
 5. The electronicsystem of claim 1, wherein the operations comprise: analyzing themonitoring system data collected by the component of the monitoringsystem; determining, based on the analysis of the monitoring system datacollected by the component of the monitoring system, that the componentof the monitoring system is not functioning properly; and providing, tothe wearable electronic device for display at the heads-up display ofthe wearable electronic device, an indication that the component of themonitoring system is not functioning properly.
 6. The electronic systemof claim 1, wherein the operations comprise: before receiving the dataidentifying the component of the monitoring system, receiving a requestfrom the wearable electronic device to configure the monitoring systemto a particular state; configuring the monitoring system to theparticular state based on receiving the request to configure themonitoring system to the particular state; and accessing the monitoringsystem data collected by the component of the monitoring system afterconfiguring the monitoring system to the particular state.
 7. Theelectronic system of claim 1, wherein: receiving the data identifyingthe component of the monitoring system comprises receiving dataidentifying the component of the monitoring system and a request to testthe component of the monitoring system from the wearable electronicdevice; accessing the monitoring system data collected by the componentof the monitoring system comprises: transmitting data to the componentof the monitoring system that initializes a test of the component of themonitoring system, receiving monitoring system data from the componentof the monitoring system in response to transmitting the data to thecomponent of the monitoring system that initializes the test of thecomponent of the monitoring system, analyzing the monitoring system datareceived from the component of the monitoring system, and determining,based on the analysis of the monitoring data received from the componentof the monitoring system, that the component of the monitoring systemsuccessfully completed the test; and providing at least a portion of themonitoring system data collected by the component of the monitoringsystem comprises providing, to the wearable electronic device fordisplay at the heads-up display of the wearable electronic device, dataindicating that the component of the monitoring system successfullycompleted the test.
 8. The electronic system of claim 1, wherein:receiving the data identifying the component of the monitoring systemcomprises receiving data identifying the component of the monitoringsystem and a request to test the component of the monitoring system fromthe wearable electronic device; accessing the monitoring system datacollected by the component of the monitoring system comprises:transmitting data to the component of the monitoring system thatinitializes a test of the component of the monitoring system, receivingmonitoring system data from the component of the monitoring system inresponse to transmitting the data to the component of the monitoringsystem that initializes the test of the component of the monitoringsystem, analyzing the monitoring system data received from the componentof the monitoring system, and determining, based on the analysis of themonitoring system data received from the component of the monitoringsystem, that the component of the monitoring system failed the test; andproviding at least a portion of the monitoring system data collected bythe component of the monitoring system comprises providing, to thewearable electronic device for display at the heads-up display of thewearable electronic device, data indicating that the component of themonitoring system failed the test.
 9. The electronic device of claim 8,wherein the operations comprise: in response to determining that thecomponent of the monitoring system failed the test, determining, basedat least on the monitoring system data received from the component ofthe monitoring system, an error for the component of the monitoringsystem; determining troubleshooting information for the component of themonitoring system that is specific to the determined error for thecomponent of the monitoring system; and providing the troubleshootinginformation to the wearable electronic device for display at theheads-up display of the wearable electronic device.
 10. The electronicdevice of claim 1, wherein the operations comprise: receiving dataidentifying a second component of the monitoring system from thewearable electronic device; accessing, based on the data identifying thesecond component of the monitoring system, monitoring system datacollected by the second component of the monitoring system; andproviding, to the wearable electronic device for display at the heads-updisplay of the wearable electronic device, at least a portion of themonitoring system data collected by the second component of themonitoring system, such that the heads-up display of the wearableelectronic device displays portions of the monitoring system datacollected by each of the identified components of the monitoring system.11. The electronic device of claim 1, wherein the operations comprise:accessing data specifying installation instructions for the component ofthe monitoring system; and providing, to the wearable electronic devicefor display at the heads-up display of the wearable electronic device,at least a portion of the installation instructions for the component ofthe monitoring system.
 12. The electronic device of claim 1, wherein theoperations comprise: accessing content associated with the component ofthe monitoring system, wherein the content associated with the componentof the monitoring system is one of video content or image content thatis associated with the component of the monitoring system and providesinstructions relating to the component of the monitoring system; andproviding, to the wearable electronic device for display at the heads-updisplay of the wearable electronic device, at least a portion of thecontent associated with the component of the monitoring system.
 13. Theelectronic device of claim 1, wherein the operations comprise:receiving, from the wearable electronic device, one of image data orvideo data, the video data or image data being obtained by a camera ofthe wearable electronic device; providing the image data or video datafor display at a computer associated with a remote user, the remote userbeing an installer associated with the monitoring system; receiving,from the computer associated with the remote user, information specifiedby the remote user; and providing, to the wearable electronic device fordisplay at the heads-up display of the wearable electronic device, atleast a portion of information provided by the remote user.
 14. A methodcomprising: receiving data identifying a component of a monitoringsystem from a wearable electronic device that is associated with themonitoring system, wherein the monitoring system is associated with aproperty and includes components that are fixed within the property andthat are configured to sense attributes of the property, and wherein thewearable electronic device includes a heads-up display and communicateswith the monitoring system over a wireless network; accessing, based onthe data identifying the component of the monitoring system, monitoringsystem data collected by the component of the monitoring system; andproviding, to the wearable electronic device for display at the heads-updisplay of the wearable electronic device, at least a portion of themonitoring system data collected by the component of the monitoringsystem.
 15. The method of claim 14, wherein the component of themonitoring system is a camera associated with the monitoring system, andwherein: accessing monitoring system data collected by the component ofthe monitoring system comprises accessing video or image data collectedby the camera associated with the monitoring system; and providing atleast a portion of the monitoring system data collected by the componentof the monitoring system comprises providing at least a portion of thevideo or image data collected by the camera associated with themonitoring system to the wearable electronic device for display at theheads-up display of the wearable electronic device.
 16. The method ofclaim 14, wherein the component of the monitoring system is a sensorassociated with the monitoring system, and wherein: accessing monitoringsystem data collected by the component of the monitoring systemcomprises accessing sensor data collected by the sensor associated withthe monitoring system; and providing at least a portion of themonitoring system data collected by the component of the monitoringsystem comprises providing at least a portion of the sensor datacollected by the sensor associated with the monitoring system to thewearable electronic device for display at the heads-up display of thewearable electronic device.
 17. The method of claim 14, comprising:before receiving the data identifying the component of the monitoringsystem, receiving a request from the wearable electronic device toconfigure the monitoring system to a particular state; configuring themonitoring system to the particular state based on receiving the requestto configure the monitoring system to the particular state; andaccessing the monitoring system data collected by the component of themonitoring system after configuring the monitoring system to theparticular state.
 18. The method of claim 14, wherein the operationscomprise: receiving data identifying a second component of themonitoring system from the wearable electronic device; accessing, basedon the data identifying the second component of the monitoring system,monitoring system data collected by the second component of themonitoring system; and providing, to the wearable electronic device fordisplay at the heads-up display of the wearable electronic device, atleast a portion of the monitoring system data collected by the secondcomponent of the monitoring system, such that the heads-up display ofthe wearable electronic device displays portions of the monitoringsystem data collected by each of the identified components of themonitoring system.
 19. The method of claim 14, wherein the operationscomprise: accessing data specifying installation instructions for thecomponent of the monitoring system; and providing, to the wearableelectronic device for display at the heads-up display of the wearableelectronic device, at least a portion of the installation instructionsfor the component of the monitoring system.
 20. The method of claim 14,wherein the operations comprise: accessing content associated with thecomponent of the monitoring system, wherein the content associated withthe component of the monitoring system is one of video content or imagecontent that is associated with the component of the monitoring systemand provides instructions relating to the component of the monitoringsystem; and providing, to the wearable electronic device for display atthe heads-up display of the wearable electronic device, at least aportion of the content associated with the component of the monitoringsystem.